home *** CD-ROM | disk | FTP | other *** search
-
-
-
- XXXXIIIInnnniiiittttTTTThhhhrrrreeeeaaaaddddssss((((3333XXXX11111111)))) XXXX VVVVeeeerrrrssssiiiioooonnnn 11111111 ((((RRRReeeelllleeeeaaaasssseeee 6666....3333)))) XXXXIIIInnnniiiittttTTTThhhhrrrreeeeaaaaddddssss((((3333XXXX11111111))))
-
-
-
- NNNNAAAAMMMMEEEE
- XInitThreads, XLockDisplay, XUnlockDisplay - multi-threading
- support
-
- SSSSYYYYNNNNTTTTAAAAXXXX
- Status XInitThreads();
-
- void XLockDisplay(_d_i_s_p_l_a_y)
- Display *_d_i_s_p_l_a_y;
-
- void XUnlockDisplay(_d_i_s_p_l_a_y)
- Display *_d_i_s_p_l_a_y;
-
- AAAARRRRGGGGUUUUMMMMEEEENNNNTTTTSSSS
- _d_i_s_p_l_a_y Specifies the connection to the X server.
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- The _X_I_n_i_t_T_h_r_e_a_d_s function initializes Xlib support for
- concurrent threads. This function must be the first Xlib
- function a multi-threaded program calls, and it must
- complete before any other Xlib call is made. This function
- returns a nonzero status if initialization was successful;
- otherwise, it returns zero. On systems that do not support
- threads, this function always returns zero.
-
- It is only necessary to call this function if multiple
- threads might use Xlib concurrently. If all calls to Xlib
- functions are protected by some other access mechanism (for
- example, a mutual exclusion lock in a toolkit or through
- explicit client programming), Xlib thread initialization is
- not required. It is recommended that single-threaded
- programs not call this function.
-
-
- The _X_L_o_c_k_D_i_s_p_l_a_y function locks out all other threads from
- using the specified display. Other threads attempting to
- use the display will block until the display is unlocked by
- this thread. Nested calls to _X_L_o_c_k_D_i_s_p_l_a_y work correctly;
- the display will not actually be unlocked until
- _X_U_n_l_o_c_k_D_i_s_p_l_a_y has been called the same number of times as
- _X_L_o_c_k_D_i_s_p_l_a_y. This function has no effect unless Xlib was
- successfully initialized for threads using _X_I_n_i_t_T_h_r_e_a_d_s.
-
- The _X_U_n_l_o_c_k_D_i_s_p_l_a_y function allows other threads to use the
- specified display again. Any threads that have blocked on
- the display are allowed to continue. Nested locking works
- correctly; if _X_L_o_c_k_D_i_s_p_l_a_y has been called multiple times by
- a thread, then _X_U_n_l_o_c_k_D_i_s_p_l_a_y must be called an equal number
- of times before the display is actually unlocked. This
- function has no effect unless Xlib was successfully
- initialized for threads using _X_I_n_i_t_T_h_r_e_a_d_s.
-
-
-
-
- Page 1 (printed 4/30/98)
-
-
-
-
-
-
- XXXXIIIInnnniiiittttTTTThhhhrrrreeeeaaaaddddssss((((3333XXXX11111111)))) XXXX VVVVeeeerrrrssssiiiioooonnnn 11111111 ((((RRRReeeelllleeeeaaaasssseeee 6666....3333)))) XXXXIIIInnnniiiittttTTTThhhhrrrreeeeaaaaddddssss((((3333XXXX11111111))))
-
-
-
- NNNNOOOOTTTTEEEESSSS
- The SGI implementation of Xlib supports concurrent threads
- only for the POSIX thread programming model (pthreads).
- _X_I_n_i_t_T_h_r_e_a_d_s will return zero if the application is not
- linked with the pthread run-time library. See the
- pthreads(5) man page for information about creating a
- pthread process.
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- pthreads(5)
- _X_l_i_b - _C _L_a_n_g_u_a_g_e _X _I_n_t_e_r_f_a_c_e
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Page 2 (printed 4/30/98)
-
-
-
-